Methods and systems to reroute data in a data network

ABSTRACT

An example method involves, when a first quality of service parameter for a failed logical circuit is equal to or less than a second quality of service parameter for a logical failover circuit, rerouting data from the failed logical circuit to the logical failover circuit without requiring authorization from a customer to communicate the data at the second quality of service parameter. When the second quality of service parameter for the logical failover circuit is a lower level of quality than the first quality of service parameter for the failed logical circuit: a customer is prompted for an authorization to communicate the data via the logical failover circuit at the second quality of service parameter; when the authorization is received, the data is rerouted from the failed logical circuit to the logical failover circuit; and when the authorization is denied, the data is not rerouted to the logical failover circuit.

PRIORITY APPLICATION

This is a continuation of U.S. patent application Ser. No. 13/547,474,filed on Jul. 12, 2012, which is a continuation of U.S. patentapplication Ser. No. 10/744,555, filed Dec. 23, 2003, now U.S. Pat. No.8,223,632, all of which are hereby incorporated herein by reference intheir entireties.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to U.S. patent application Ser. No.10/348,077, entitled “Method and System for Obtaining LogicalPerformance Data for a Circuit in a Data Network,” filed on Jan. 21,2003, and U.S. patent application Ser. No. 10/348,592, entitled “Methodand System for Provisioning and Maintaining a Circuit in a DataNetwork,” filed on Jan. 21, 2003. This application is also related toand filed concurrently with U.S. patent application Ser. No. 10/745,117,entitled “Method And System For Providing A Failover Circuit ForRerouting Logical Circuit Data In A Data Network,” filed on Dec. 23,2003, U.S. patent application Ser. No. 10/744,281, entitled “Method AndSystem For Utilizing A Logical Failover Circuit For Rerouting DataBetween Data Networks,” filed on Dec. 23, 2003, U.S. patent applicationSer. No. 10/745,047, entitled “Method And System For AutomaticallyRenaming Logical Circuit Identifiers For Rerouted Logical Circuits In AData Network,” filed on Dec. 23, 2003, U.S. patent application Ser. No.10/745,170, entitled “Method And System For Automatically Identifying ALogical Circuit Failure In A Data Network,” filed on Dec. 23, 2003, U.S.patent application Ser. No. 10/744,921, entitled “Method and System ForAutomatically Rerouting Logical Circuit Data In A Data Network,” filedon Dec. 23, 2003, U.S. patent application Ser. No. 10/745,168, entitled“Method And System For Automatically Rerouting Logical Circuit Data In AVirtual Private Network,” filed on Dec. 23, 2003, U.S. patentapplication Ser. No. 10/745,116, entitled “Method And System ForAutomatically Rerouting Data From An Overbalanced Logical Circuit In AData Network,” filed on Dec. 23, 2003, U.S. patent application Ser. No.10/744,555, entitled “Method And System For Real Time SimultaneousMonitoring Of Logical Circuits In A Data Network,” filed on Dec. 23,2003. All of the above-referenced applications are assigned to the sameassignee as the present application and are expressly incorporatedherein by reference.

TECHNICAL FIELD

The present disclosure relates to the routing of data using logicalcircuits in a data network. More particularly, the present disclosure isrelated to rerouting data in a data network.

BACKGROUND

Data networks contain various network devices, such as switches, forsending and receiving data between two locations. For example, framerelay and Asynchronous Transfer Mode (“ATM”) networks containinterconnected network devices that allow data packets or cells to bechanneled over a circuit through the network from a host device to aremote device. For a given network circuit, the data from a host deviceis delivered to the network through a physical circuit such as a T1 linethat links to a switch of the network. The remote device thatcommunicates with the host through the network also has a physicalcircuit to a switch of the network. A network circuit also includes alogical circuit which includes a variable communication path for databetween the switches associated with the host and the remote device.Logical circuits may be provisioned with certain quality of service(“QoS”) parameters or traffic descriptors which describe the level ofpriority given to data communicated through a data network. For example,an ATM circuit provisioned for constant bit rate (“CBR”) service carrieshigher priority data (such as voice traffic) than unspecified bit rate(“UBR”) service. CBR service assures that high priority data, such asvoice traffic, which is sensitive to delay, is communicated at aguaranteed data rate for quality service. Conversely, UBR serviceassures no quality guarantees making data communicated at this levelhighly susceptible to delay and network congestion.

In large-scale networks, the host and remote end devices of a networkcircuit may be connected across different local access and transportareas (“LATAs”) which may in turn be connected to one or moreInter-Exchange Carriers (“IEC”) for transporting data between the LATAs.These connections are made through physical trunk circuits utilizingfixed logical connections known as Network-to-Network Interfaces(“NNIs”).

Periodically, failures may occur to the trunk circuits or the NNIs ofnetwork circuits in large-scale networks causing lost data. Currently,such failures are handled by dispatching technicians on each end of thenetwork circuit (i.e., in each LATA) in response to a reported failureto manually repair the logical and physical connections making up thenetwork circuit. Some modern data networks also include redundantphysical connections for rerouting data from failed physical connectionsin a network circuit while the failed physical connections are beingrepaired. These “self-healing” networks however, do not account forexisting QoS parameters for failed network circuits, resulting in thedata being communicated at the lowest available quality of service(e.g., UBR) over the redundant physical connections. As a result, thecommunication of high priority data packets or cells from the failedcircuit may be delayed or dropped entirely.

It is with respect to these considerations and others that the presentinvention has been made.

SUMMARY

In accordance with the present disclosure, the above and other problemsare solved by a method and system for prioritized rerouting of logicalcircuit data in a data network. When a logical circuit failure isdetected, the data in the logical circuit may be rerouted to a logicalfailover circuit at the same quality of service provisioned for thefailed logical circuit.

According to the method, logical circuit failure is identified in thedata network. Following the identification of the logical circuitfailure, a quality of service parameter for the communication of data inthe failed logical circuit is determined. Then a logical failovercircuit comprising an alternate communication path for communicating thedata in the failed logical circuit is identified. Next, a quality ofservice parameter for the communication of data in the logical failovercircuit is determined. If the quality of service parameter for thefailed logical circuit is equal to the quality of service parameter forthe logical failover circuit, then the data from the failed logicalcircuit is rerouted to the logical failover circuit.

The method may further include rerouting the data to the logicalfailover circuit when the quality of service parameter for the failovercircuit is indicative of a lower level of quality if authorization isreceived for the reroute. The quality of service parameter may include atraffic descriptor for logical circuit data. The quality of serviceparameter may be a variable frame relay (“VFR”) real time parameter, aVFR non-real time parameter, a constant bit rate (“CBR”) parameter, avariable bit rate (“VBR”) parameter, or an unspecified bit rate (“UBR”)parameter.

The logical failover circuit may include a dedicated failover logicalconnection in a failover data network. The logical circuit and thelogical failover circuit may be identified by logical circuitidentifiers. The logical circuit identifiers may be data link connectionidentifiers (“DLCIs”) or virtual path/virtual circuit identifiers(“VPI/VCIs”). The dedicated failover logical connection may be anetwork-to-network interface (“NNI”). The logical failover circuit maybe either a permanent virtual circuit (“PVC”) or a switched virtualcircuit (“SVC”). The data network may be either frame relay network oran asynchronous transfer mode (“ATM”) network.

In accordance with other aspects, the present disclosure relates to asystem for prioritized rerouting of logical circuit data in a datanetwork. The system includes a network device for communicating statusinformation for a logical circuit in the data network. The logicalcircuit includes a communication path for communicating data. The systemalso includes a logical element module, in communication with thenetwork device, for receiving the status information for the logicalcircuit in the data network. The system further includes a networkmanagement module, in communication with the logical element module, foridentifying a failed logical circuit in the data network, determining aquality of service parameter for the communication of data in the failedlogical circuit, identifying a logical failover circuit including analternate communication path for communicating the data in the failedlogical circuit, and determining a quality of service parameter for thecommunication of data in the logical failover circuit. If the quality ofservice parameter for the failed logical circuit is equal to the qualityof service parameter for the logical failover circuit, then the data isrerouted to the logical failover circuit. If the quality of serviceparameter for the failed logical circuit is not equal to the quality ofservice parameter for the logical failover circuit, then authorizationis obtained prior to rerouting the data to the logical failover circuit.

In accordance with still other aspects, the present disclosure relatesto a system for prioritized rerouting of logical circuit data in a datanetwork. The system includes a network device for communicating statusinformation for a logical circuit in the data network. The logicalcircuit includes a communication path for communicating data. The systemalso includes a logical element module, in communication with thenetwork device, for receiving the status information for the logicalcircuit in the data network. The system further includes a networkmanagement module, in communication with the logical element module, foridentifying a failed logical circuit in the data network, determining aquality of service parameter for the communication of data in the failedlogical circuit, and provisioning a logical failover circuit comprisingan alternate communication path for communicating the data in the failedlogical circuit. The logical failover circuit is provisioned having aquality of service parameter equal to the quality of service parameterfor the failed logical circuit. The network management module thenreroutes the data from the failed logical circuit to the provisionedlogical failover circuit.

These and various other features as well as advantages will be apparentfrom a reading of the following detailed description and a review of theassociated drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a data network according to an embodiment of thedisclosure.

FIG. 2 illustrates a local access and transport area (“LATA”) in thedata network of FIG. 1, according to an embodiment of the disclosure.

FIG. 3 illustrates a network management system which may be utilized forprioritized rerouting of logical circuit data in the data network ofFIG. 1, according to an embodiment of the disclosure.

FIG. 4 illustrates a failover data network for rerouting logical circuitdata, according to an embodiment of the disclosure.

FIG. 5 illustrates a flowchart describing logical operations forprioritized rerouting of logical circuit data in a data network of FIG.1, according to an embodiment of the disclosure.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present disclosure provide for a method and systemfor prioritized rerouting of logical circuit data in a data network.When a logical circuit failure is detected, the data in the logicalcircuit may be rerouted to a logical failover circuit at the samequality of service provisioned for the failed logical circuit. In thefollowing detailed description, references are made to the accompanyingdrawings that form a part hereof, and in which are shown by way ofillustration specific embodiments or examples. Referring now to thedrawings, in which like numerals represent like elements through theseveral figures, aspects of the present disclosure and the exemplaryoperating environment will be described.

Embodiments of the present disclosure may be generally employed in adata network 2 as shown in FIG. 1. The data network 2 includes localaccess and transport areas (“LATAs”) 5 and 15 which are connected by anInter-Exchange Carrier (“IEC”) 10. It should be understood that theLATAs 5 and 15 may be data networks operated by a commonly owned LocalExchange Carrier (“LEC”). It should be further understood that the IEC10 may include one or more data networks which may be operated by acommonly owned IEC. It will be appreciated by those skilled in the artthat the data network 2 may be a frame relay network, asynchronoustransfer mode (“ATM”) network, or any other network capable ofcommunicating data conforming to Layers 2-4 of the Open SystemsInterconnection (“OSI”) model developed by the International StandardsOrganization, incorporated herein by reference. It will be appreciatedthat these networks may include, but are not limited to, communicationsprotocols conforming to the Multiprotocol Label Switching Standard(“MPLS”) networks and the Transmission Control Protocol/InternetProtocol (“TCP/IP”), which are known to those skilled in the art.

The data network 2 includes a network circuit which channels databetween a host device 112 and a remote device 114 through the LATA 5,the IEC 10, and the LATA 15. It will be appreciated by those skilled inthe art that the host and remote devices 112 and 114 may be local areanetwork (“LAN”) routers, LAN bridges, hosts, front end processors, FrameRelay Access Devices (“FRADs”), or any other device with a frame relay,ATM, or network interface. It will be further appreciated that in thedata network 2, the LATAs 5 and 15 and the IEC 10 may include networkelements (not shown) which support interworking to enable communicationsbetween host and remote devices supporting dissimilar protocols. Networkelements in a data network supporting interworking may translate framerelay data packets or frames sent from a host FRAD to ATM data packetsor cells so that a host device may communicate with a remote devicehaving an ATM interface. The LATAs 5 and 15 and the IEC 10 may furtherinclude one or more interconnected network elements, such as switches(not shown), for transmitting data. An illustrative LEC data networkwill be discussed in greater detail in the description of FIG. 2 below.

The network circuit between the host device 112 and the remote device114 in the data network 2 includes a physical circuit and a logicalcircuit. As used in the foregoing description and the appended claims, aphysical circuit is defined as the physical path that connects the endpoint of a network circuit to a network device. For example, thephysical circuit of the network circuit between the host device 112 andthe remote device 114 includes the physical connection 121 between thehost device 112 and the LATA 5, the physical connection 106 between theLATA 5 and the IEC 10, the physical connection 108 between the IEC 10and the LATA 15, and the physical connection 123 between the LATA 15 andthe remote device 114. Routers and switches within the LATAs 5 and 15and the IEC 10 carry the physical signal between the host and remote enddevices 112 and 114 through the physical circuit.

It should be understood that the host and remote devices may beconnected to the physical circuit described above using user-to-networkinterfaces (“UNIs”). As is known to those skilled in the art, an UNI isthe physical demarcation point between a user device (e.g, a hostdevice) and a public data network. It will further be understood bythose skilled in the art that the physical connections 106 and 108 mayinclude trunk circuits for carrying the data between the LATAs 5 and 15and the IEC 10. It will be further understood by those skilled in theart that the connections 121 and 123 may be any of various physicalcommunications media for communicating data such as a 56 Kbps line or aT1 line carried over a four-wire shielded cable or over a fiber opticcable.

As used in the foregoing description and the appended claims, a logicalcircuit is defined as a portion of the network circuit wherein data issent over variable communication data paths or logical connectionsestablished between the first and last network devices within a LATA orIEC network and over fixed communication data paths or logicalconnections between LATAs (or between IECs). Thus, no matter what paththe data takes within each LATA or IEC, the beginning and end of eachlogical connection between networks will not change. For example, thelogical circuit of the network circuit in the data network 2 may includea variable communication path within the LATA 5 and a fixedcommunication path (i.e., the logical connection 102) between the LATA 5and the IEC 10. It will be understood by those skilled in the art thatthe logical connections 102 and 104 in the data network 2 may includenetwork-to-network interfaces (“NNIs”) between the last sending switchin a LATA and the first receiving switch in an IEC. It should beunderstood that in data networks supporting interworking (i.e.,utilizing both frame relay and ATM devices), data may be communicatedover frame relay circuits over the UNI connections between the host orremote device and the LATA (or IEC) data network, and over ATM circuitsover the NNI connections within the LATA (or IEC) data network.

As is known to those skilled in the art, each logical circuit in a datanetwork may be identified by a unique logical identifier. In frame relaynetworks, the logical identifier is called a Data Link ConnectionIdentifier (“DLCI”) while in ATM networks the logical identifier iscalled a Virtual Path Identifier/Virtual Circuit Identifier (“VPI/VCI”).In frame relay networks, the DLCI is a 10-bit address field contained inthe header of each data frame and contains identifying information forthe logical circuit as well as information relating to the destinationof the data in the frame, quality of service (“QoS”) parameters, andother service parameters for handling network congestion. For example,in the data network 2 implemented as a frame relay network, thedesignation DLCI 100 may be used to identify the logical circuit betweenthe host device 112 and the remote device 114. It will be appreciatedthat in data networks in which logical circuit data is communicatedthrough more than one carrier (e.g., an LEC and an IEC) the DLCIdesignation for the logical circuit may change in a specific carrier'snetwork. For example, in the data network 2, the designation DLCI 100may identify the logical circuit in the LATA 5 and LATA 15 but thedesignation DLCI 800 may identify the logical circuit in the IEC 10.

Illustrative QoS parameters which may be included in the DLCI include aVariable Frame Rate (“VFR”) real time parameter and a VFR non-real timeparameter. As is known to those skilled in the art, VFR real time is avariable data rate for frame relay data frames communicated over alogical circuit. Typically, VFR real-time circuits are able to toleratesmall variations in the transmission rate of data (i.e., delay) andsmall losses of frames. Typical applications for VFR real time circuitsmay include, but are not limited to, voice and some types of interactivevideo. VFR non-real time circuits also communicate data frames at avariable data rate but are able to tolerate higher variations in thetransmission rate and thus more delay as these circuits are typically“bursty” (i.e., data is transmitted in short, uneven spurts) in nature.Typical applications for VFR non-real time circuits include, but arelimited to, inter-LAN communications and Internet traffic.

Illustrative service parameters which may be included in the DLCIinclude a Committed Information Rate (“CIR”) parameter and a CommittedBurst Size (“Be”) parameter. As is known to those skilled in the art,the CIR represents the average capacity of the logical circuit and theBe represents the maximum amount of data that may be transmitted. Itwill be appreciated that the logical circuit may be provisioned suchthat when the CIR or the Be is exceeded, the receiving switch in thedata network will discard the frame. It should be understood that thelogical circuit parameters are not limited to CR and Be and that otherparameters known to those skilled in the art may also be provisioned,including, but not limited to, Burst Excess Size (“Be”) and CommittedRate Measurement Interval (“Tc”).

In ATM networks, the VPI/VCI is an address field contained in the headerof each ATM data cell and contains identifying information for thelogical circuit as well as information specifying a data cell'sdestination, QoS parameters, and specific bits which may indicate, forexample, the existence of congestion in the network and a threshold fordiscarding cells. Illustrative QoS parameters which may be included inthe VPI/VCI include a Committed Bit Rate (“CBR”) parameter, a VariableBit Rate (“VBR”) parameter, and an Unspecified Bit Rate (“UBR”)parameter. As is known to those skilled in the art, CBR defines aconstant data rate for ATM cells communicated over a logical circuit.Typically, CBR circuits are given the highest priority in a data networkand are very intolerant to delay. Typical applications for CBR circuitsmay include, but are not limited to, video conferencing, voice,television and video-on demand. VBR circuits communicate ATM cells at avariable data rate and are able to tolerate varying degrees of delay.Similar to frame relay variable service parameters, VBR circuits may befurther subdivided into VBR real time and VBR non-real time. VBRnon-real time circuits are able to tolerate more delay. Typicalapplications for ATM VBR circuits may include the same applications asframe relay VFR circuits. UBR circuits communicate ATM cells at anunspecified bit rate and are extremely tolerant to delay. UBR circuitsare typically reserved for non-time sensitive applications such as filetransfer, email, and message and image retrieval.

It should be understood that the logical circuit in the data network 2may be a permanent virtual circuit (“PVC”) available to the network atall times or a temporary or a switched virtual circuit (“SVC”) availableto the network only as long as data is being transmitted. It should beunderstood that the data network 2 may further include additionalswitches or other interconnected network elements (not shown) creatingmultiple paths within each LATA and IEC for defining each PVC or SVC inthe data network. It will be appreciated that the data communicated overthe logical connections 102 and 104 may be physically carried by thephysical connections 106 and 108.

The data network 2 may also include a failover network 17 for reroutinglogical circuit data, according to an embodiment of the disclosure. Thefailover network 17 may include a network failover circuit includingphysical connections 134 and 144 and logical connections 122 and 132 forrerouting logical circuit data in the event of a failure in the networkcircuit between the host device 112 and the remote device 114. Thefailover network 17 will be described in greater detail in thedescription of FIG. 4 below. The data network 2 may also include anetwork management system 175 in communication with the LATA 5, the LATA15, and the failover network 17. The network management system 175 maybe utilized to obtain status information for the logical and physicalcircuit between the host device, 112 and the remote device 114. Thenetwork management system 175 may also be utilized for rerouting logicaldata in the data network 2 between the host device 112 and the remotedevice 114. The network management system 175 will be discussed ingreater detail in the description of FIG. 3 below.

FIG. 2 illustrates the LATA 5 in the data network 2 described in FIG. 1above, according to an embodiment of the present disclosure. As shown inFIG. 2, the LATA 5 includes interconnected network devices such asswitches 186, 187, and 188. It will be appreciated that the data network2 may also contain other interconnected network devices and elements(not shown) such as digital access and cross connect switches (“DACS”),channel service units (“CSUs”), and data service units (“DSUs”). Asdiscussed above in the description of FIG. 1, the connection data pathsof a logical circuit within a data network may vary between the firstand last network devices in a data network. For example, as shown inFIG. 2, the logical circuit in the LATA 5 may include the communicationpath 185 between the switches 186 and 188 or the communication path 184between the switches 186, 187, and 188. As discussed above, it should beunderstood that the actual path taken by data through the LATA 5 is notfixed and may vary from time to time, such as when automatic reroutingtakes place.

It will be appreciated that the switches 186, 187, and 188 may include asignaling mechanism for monitoring and signaling the status of thelogical circuit in the data network 2. Each time a change in the statusof the logical circuit is detected (e.g., a receiving switch beginsdropping frames), the switch generates an alarm or “trap” which may thenbe communicated to a management station, such as a logical elementmodule (described in detail in the description of FIG. 3 below), in thenetwork management system 175. The trap may include, for example, statusinformation indicating network congestion.

In one embodiment, the signaling mechanism may be in accord with a LocalManagement Interface (“LMI”) specification, which provides for thesending and receiving of “status inquiries” between a data network and ahost or remote device. The LMI specification includes obtaining statusinformation through the use of special management frames (in frame relaynetworks) or cells (in ATM networks). In frame relay networks, forexample, the special management frames monitor the status of logicalconnections and provide information regarding the health of the network.In the data network 2, the host and remote devices 112 and 114 receivestatus information from the switches in the individual LATAs they areconnected to in response to a status request sent in a specialmanagement frame or cell. The LMI status information may include, forexample, whether or not the logical circuit is congested or whether ornot the logical circuit has failed. It should be understood that theparameters and the signaling mechanism discussed above are optional andthat other parameters and mechanisms may also be utilized to obtainconnection status information for a logical circuit.

FIG. 3 illustrates the network management system 175 which may beutilized for prioritized rerouting of logical circuit data in the datanetwork of FIG. 1, according to an embodiment of the disclosure. Thenetwork management system 175 includes a service order system 160, anetwork database 170, a logical element module 153, a physical elementmodule 155, a network management module 176, and a test module 180. Theservice order system 160 is utilized in the data network 2 for receivingservice orders for provisioning network circuits. The service orderincludes information defining the transmission characteristics or QoSparameters for the logical circuit portion of the network circuit. Theservice order also contains the access speed, CIR, burst rates, andexcess burst rates. The service order system 160 communicates theservice order information to a network database 170 over managementtrunk 172. The network database 170 assigns and stores the parametersfor the physical circuit portion of the network circuit such as a portnumber on the switch 186 for transmitting data over the physicalconnection 121 to and from the host device 112.

The network database 170 may also be in communication with an operationssupport system (not shown) for assigning physical equipment to thenetwork circuit and for maintaining an inventory of the physicalassignments for the network circuit. An illustrative operations supportsystem is “TIRKS”® (Trunks Integrated Records Keeping System) marketedby TELECORDIA™ TECHNOLOGIES, Inc. of Morristown, N.J. The networkdatabase 170 may also be in communication with a Work ForceAdministration and Control system (“WFA/C”) (not shown) used to assignresources (i.e., technicians) to work on installing the physicalcircuit.

The network management system 175 also includes the logical elementmodule 153 which is in communication with the switches in the datanetwork 2 through management trunks 183. The logical element module 153runs a network management application program to monitor the operationof logical circuits which includes receiving trap data generated by theswitches which indicate the status of logical connections. The trap datamay be stored in the logical element module 153 for later analysis andreview. The logical element module 153 is also in communication with thenetwork database 170 via management trunks 172 for accessing informationregarding logical circuits such as the logical identifier data. Thelogical identifier data may include, for example, the DLCI or VPI/VCIheader information for each data frame or cell in the logical circuitincluding the circuit's destination and QoS parameters. The logicalelement module 153 may consist of terminals (not shown) that display amap-based graphical user interface (“GUI”) of the logical connections inthe data network. An illustrative logical element module is theNAVISCORE™ system marketed by LUCENT TECHNOLOGIES, Inc. of Murray Hill,N.J.

The network management system 175 further includes the physical elementmodule 155 in communication with the physical connections of the networkcircuit via management trunks (not shown). The physical element module155 runs a network management application program to monitor theoperation and retrieve data regarding the operation of the physicalcircuit. The physical element module 155 is also in communication withthe network database 170 via management trunks 172 for accessinginformation regarding physical circuits, such as line speed. Similar tothe logical element module 153, the physical logical element module 155may also consist of terminals (not shown) that display a map-based GUIof the physical connections in the LATA 5. An illustrative physicalelement module is the Integrated Testing and Analysis System (“INTAS”),marketed by TELECORDIA™ TECHNOLOGIES, Inc. of Morristown, N.J., whichprovides flow-through testing and analysis of telephony, services.

The physical element module 155 troubleshoots the physical connectionsfor a physical circuit by communicating with test module 180, whichinterfaces with the physical connections via test access point 156. Thetest module 180 obtains the status of the physical circuit bytransmitting “clean” test signals to test access point 156 (shown inFIG. 2) which “loops back” the signals for detection by the test module180. It should be understood that there may be multiple test accesspoints on each of the physical connections for the physical circuit.

The network management system 175 further includes the networkmanagement module 176 which is in communication with the service ordersystem 160, the network database 170, the logical element module 153,and the physical element module 155 through communications channels 172.It should be understood that in one embodiment, the network managementsystem 175 may also be in communication with the LATA 15, the IEC 10,and the fail over network 17. The communications channels 172 may be ona LAN. The network management module 176 may consist of terminals (notshown), which may be part of a general-purpose computer system thatdisplays a map-based GUI of the logical connections in data networks.The network management module 176 may communicate with the logicalelement module 153 and the physical element module 155 using a CommonObject Request Broker Architecture (“CORBA”). As is known to thoseskilled in the art, CORBA is an open, vendor-independent architectureand infrastructure which allows different computer applications to worktogether over one or more networks using a basic set of commands andresponses. The network management module 176 may also serve as aninterface for implementing logical operations to provision and maintainnetwork circuits. The logical operations may be implemented as machineinstructions stored locally or as instructions retrieved from thelogical and physical element modules 153 and 155. An illustrative methoddetailing the provisioning and maintenance of network circuits in a datanetwork is presented in U.S. patent application Ser. No. 10/348,592,entitled “Method And System For Provisioning And Maintaining A CircuitIn A Data Network,” filed on Jan. 23, 2003, and assigned to the sameassignee as this application, which is expressly incorporated herein byreference. An illustrative network management module is the BroadbandNetwork Management System® (“BBNMS”) marketed by TELECORDIA™TECHNOLOGIES, Inc. of Morristown, N.J.

FIG. 4 illustrates an illustrative failover data network for reroutinglogical circuit data, according to one embodiment of the presentdisclosure. As shown in FIG. 4, the failover network 17 includes an IEC20, a LATA 25, and an IEC 30. The failover network further includes anetwork failover circuit which includes a physical failover circuit anda logical failover circuit. The physical failover circuit includes thephysical connection 134 between the LATA 5 (shown in FIG. 1) and the IEC20, the physical connection 136 between the IEC 20 and the LATA 25, thephysical connection 138 between the LATA 25 and the IEC 30, and thephysical connection 144 between the IEC 30 and the LATA 15 (shown inFIG. 1). Similarly, the logical failover circuit may include the logicalconnection 122 between the LATA 5 (shown in FIG. 1) and the IEC 20, thelogical connection 124 between the IEC 20 and the LATA 25, the logicalconnection 126 between the LATA 25 and the IEC 30, and the logicalconnection 132 between the IEC 30 and the LATA 15 (shown in FIG. 1). Itshould be understood that in one embodiment, the network failovercircuit illustrated in the failover network 17 may include a dedicatedphysical circuit and a dedicated logical circuit provisioned by anetwork service provider serving the LATAs 5, 15, and 25 and the IECs 20and 30, for rerouting logical data from a failed logical circuit.

FIG. 5 illustrates a flowchart describing logical operations 500 forprioritized rerouting of logical circuit data in the data network 2 ofFIG. 1, according to an embodiment of the disclosure. It will beappreciated that the logical operations 500 may be initiated when acustomer report of a network circuit failure is received in the datanetwork 2. For example, a customer at the remote device 114 maydetermine that the remote device 114 is dropping frames or cells sentfrom the host device 112 (e.g., by reviewing LMI status information inthe host device). After receiving the customer report, the networkservice provider providing the network circuit may open a trouble ticketin the service order system 160 to troubleshoot the logical circuit.

The logical operations 500 begin at operation 505 where the networkmanagement module 176 identifies a failed logical circuit in the datanetwork 2. It will be appreciated that a logical circuit failure may bebased on status information received in communications with the logicalelement module 153 to request trap data generated by one or moreswitches in the data network 2. The trap data indicates the status ofone or more logical connections making up the logical circuit. Forexample, in the data network 2 shown in FIG. 1, the “X” marking thelogical connections 102 and 104 indicates that both connections are“down beyond” the logical connections in the LATA data networks 5 and15. It will be appreciated that in this example, the logical circuitfailure lies in the IEC data network 10. An illustrative methoddetailing the identification of logical circuit failures in a datanetwork is presented in co-pending U.S. patent application Ser. No.10/745,170, entitled “Method And System For Automatically Identifying ALogical Circuit Failure In A Data Network,” filed on Dec. 23, 2003, andassigned to the same assignee as this application, which is expresslyincorporated herein by reference.

After identifying a failed logical circuit at operation 505, the logicaloperations 500 continue at operation 510 where the network managementmodule 176 determines the QoS parameter for the communication of data inthe failed logical circuit. As discussed above in the description ofFIG. 1, the QoS parameters for a logical circuit are contained withinthe DLCI (for frame relay circuits) or the VPI/VCI (for ATM circuits).The QoS parameters for logical circuits may also be stored in thenetwork database 170 after the circuits are provisioned in the datanetwork. Thus, in one embodiment of the present disclosure, the networkmanagement module 176 may determine the logical identifier for thefailed logical circuit from the trap data received from the logicalelement module 153 and then access the database 170 to determine the QoSparameter for the circuit. The logical operations then continue fromoperation 510 to operation 515.

At operation 515, the network management module 176 identifies a logicalfailover circuit for communicating failed logical circuit data over analternate communication in the data network 2. For example, if as shownin FIG. 1, it is determined that the failure in the logical circuit inthe data network 2 has been isolated to the IEC data network 10, alogical failover circuit in the failover network 17 may be automaticallyselected to reroute the logical data such that it bypasses the IEC datanetwork 10. For example, the logical failover circuit may be selectedincluding the logical connections 122, 124, 126, and 132 (as shown inFIG. 4) to reroute the logical data from the host device 112, throughthe LATA 5, the IEC 20, the LATA 25, the IEC 30, the LATA 15, andfinally to the remote device 114.

It should be understood that the network management module 176 mayselect the logical failover circuit by identifying a logical connectionor NNI in the overbalanced logical circuit. Information related to eachlogical connection in a logical circuit may be stored in the database170 including the first and second ends of the logical circuit to whichthe logical connection belongs. Once the ends of a logical circuit aredetermined by accessing the database 170, the network management module176 may select a logical failover circuit having a communication pathincluding the first and second ends of the overbalanced logical circuitfor rerouting data.

It will be appreciated that in one embodiment, the logical failovercircuit selected may be a dedicated circuit which is only utilized forrerouting logical data from the failed logical circuit (i.e., thefailover circuit does not normally communicate data traffic). In thisembodiment, the logical failover circuit may be provisioned with thesame QoS parameter as the logical circuit to which it is assigned. Inanother embodiment, the logical failover circuit may be an existinglogical circuit which is normally utilized for communicating datatraffic in the data network 2. In this embodiment, the selection of thelogical failover circuit may also include determining whether one ormore logical connections in the logical circuit are currentlycommunicating data traffic or are currently unused. If currently unused,the logical connections may be selected for rerouting logical data. Forexample, a technician at the logical element module 153 or the networkmanagement module 176 may utilize a map-based GUI displaying the logicalconnections in the LATA data networks 5 and 15 and their status. Adedicated logical failover circuit (or a currently unused logicalcircuit with available logical connections) may then be selected as alogical failover circuit for communicating logical data from a failedlogical circuit. The logical operations 500 then continue from operation515 to operation 520.

At operation 520, the network management module determines the QoSparameter for the previously identified logical failover circuit. Itwill be appreciated that the identification of the QoS parameter for thelogical failover circuit may be made by identifying the logical circuitID for the logical failover circuit and then accessing the networkdatabase 170 to retrieve the QoS parameter for the circuit. The logicaloperations 500 then continue from operation 520 to operation 525.

At operation 525 the network management module 176 compares the QoSparameters for the failed logical circuit and the logical failovercircuit to determine if they are the same. If the QoS parameters are thesame, the logical operations continue to operation 535 where the failedlogical circuit data is rerouted over the logical failover circuit. Anillustrative method detailing the rerouting of failed logical circuitsin a data network is presented in co-pending U.S. patent applicationSer. No. 10/744,921, entitled “Method And System For AutomaticallyRerouting Logical Circuit Data In A Data Network,” filed on Dec. 23,2003, and assigned to the same assignee as this application, which isexpressly incorporated herein by reference.

For example, if the network management module 176 determines that theQoS for the failed logical circuit and the logical failover circuit isCBR, then the failed logical circuit data is rerouted over the logicalfailover circuit while maintaining the same quality of service. It willbe appreciated that in data networks supporting interworking (i.e., bothframe relay and ATM devices), the network management module 176 may beconfigured to reroute logical circuit data based on similar QoSparameters from each protocol. For example, if the failed logicalcircuit has a frame relay QoS parameter of VFR real time, the networkmanagement module 176 may reroute the data to an ATM logical failovercircuit having a QoS parameter of VBR real time, since these quality ofservice parameters are defined to tolerate only small variations intransmission rates. Similarly, a failed logical circuit having an ATMQoS parameter of UBR may be rerouted over a frame relay logical failovercircuit having a QoS of VFR non-real time since both of these parametersare tolerant of delay and variable transmission rates.

If, however, at operation 525, the network management module 176determines that the QoS parameters for the failed logical circuit andthe logical failover circuit are not the same, then the logicaloperations continue from operation 525 to operation 530 where thenetwork management module 176 obtains authorization to reroute thelogical circuit data. Once authorization is received, the logicaloperations 530 then continue to operation 535 where the failed logicalcircuit data is rerouted over the logical failover circuit. It will beappreciated that authorization may be obtained if the logical failovercircuit is provisioned for a lower quality of service than the failedlogical circuit. For example, authorization may be obtained from an ATMcircuit customer with a QoS parameter of CBR to reroute logical circuitdata to a failover logical circuit with a QoS parameter of VBR realtime. It will be appreciated that in some instances, a customerunwilling to accept delay and variable transmission rates for highpriority data (such as voice) may not wish data to be rerouted over alower priority circuit. The logical operations 500 then end.

It will be appreciated that in an alternative embodiment of the presentdisclosure, the network management module 176 may be configured toprovision an appropriate logical failover in real time upon identifyinga failure in a logical circuit. In this embodiment, the networkmanagement module 176, after identifying the QoS parameter for thefailed logical circuit, may build a failover circuit with logicalconnections having the same QoS parameter for rerouting the failedlogical circuit data. It should be understood that for portions of thelogical failover circuit passing through a data network operated by adifferent carrier (such as an IEC data network), the rerouting carriermay negotiate a comparable quality of service so that quality may bemaintained between a host device and a remote device.

It will be appreciated that in one embodiment of the present disclosure,the prioritization applied to the rerouting of logical circuit datalogical circuit failover procedure may be initiated as a serviceoffering by a Local Exchange Carrier (LEC) or an Inter-Exchange Carrier(IEC) to priority customers for rerouting logical circuit data. If apriority customer is not a subscriber, the service may still beinitiated and the priority customer may be billed based on the length oftime the prioritized logical failover circuit was in use.

It will be appreciated that the embodiments of the disclosure describedabove provide for a method and system for prioritized rerouting oflogical circuit data in a data network. When a logical circuit failureis detected, the data in the logical circuit may be rerouted to alogical failover circuit at the same quality of service provisioned forthe failed logical circuit. The various embodiments described above areprovided by way of illustration only and should not be construed tolimit the invention. Those skilled in the art will readily recognizevarious modifications and changes that may be made to the presentinvention without following the example embodiments and applicationsillustrated and described herein, and without departing from the truespirit and scope of the present disclosure, which is set forth in thefollowing claims.

What is claimed is:
 1. A method to reroute logical circuit data in adata network, the method comprising: when a first quality of serviceparameter for a failed logical circuit is equal to or less than a secondquality of service parameter for a logical failover circuit, reroutingdata from the failed logical circuit to the logical failover circuitwithout requiring authorization from a customer to communicate the dataat the second quality of service parameter; and when the second qualityof service parameter for the logical failover circuit is a lower levelof quality than the first quality of service parameter for the failedlogical circuit: prompting the customer for an authorization tocommunicate the data via the logical failover circuit at the secondquality of service parameter; when the authorization is received,rerouting the data from the failed logical circuit to the logicalfailover circuit; and when the authorization is denied, not reroutingthe data to the logical failover circuit.
 2. The method of claim 1,wherein the first quality of service parameter for the failed logicalcircuit is a traffic descriptor for logical circuit data.
 3. The methodof claim 1, wherein the first quality of service parameter for thefailed logical circuit is a variable frame relay real time parameter. 4.The method of claim 1, wherein the first quality of service parameterfor the failed logical circuit is a variable frame relay non-real timeparameter.
 5. The method of claim 1, wherein the first quality ofservice parameter for the failed logical circuit is a constant bit rateparameter.
 6. The method of claim 1, wherein the first quality ofservice parameter for the failed logical circuit is a variable bit rateparameter.
 7. The method of claim 1, wherein the first quality ofservice parameter for the failed logical circuit is an unspecified bitrate parameter.
 8. An apparatus to reroute logical circuit data in adata network, the apparatus comprising: a processor; and a memory tostore machine readable instructions that, when executed by theprocessor, cause the processor to perform operations comprising: when afirst quality of service parameter for a failed logical circuit is equalto or less than a second quality of service parameter for a logicalfailover circuit, rerouting data from the failed logical circuit to thelogical failover circuit without requiring authorization from a customerto communicate the data at the second quality of service parameter; andwhen the second quality of service parameter for the logical failovercircuit is a lower level of quality than the first quality of serviceparameter for the failed logical circuit: prompting the customer for anauthorization to communicate the data via the logical failover circuitat the second quality of service parameter; when the authorization isreceived, rerouting the data from the failed logical circuit to thelogical failover circuit; and when the authorization is denied, notrerouting the data to the logical failover circuit.
 9. The apparatus ofclaim 8, wherein the first quality of service parameter for the failedlogical circuit is a traffic descriptor for logical circuit data. 10.The apparatus of claim 8, wherein the first quality of service parameterfor the failed logical circuit is a variable frame relay real timeparameter.
 11. The apparatus of claim 8, wherein the first quality ofservice parameter for the failed logical circuit is a variable framerelay non-real time parameter.
 12. The apparatus of claim 8, wherein thefirst quality of service parameter for the failed logical circuit is aconstant bit rate parameter.
 13. The apparatus of claim 8, wherein thefirst quality of service parameter for the failed logical circuit is avariable bit rate parameter.
 14. The apparatus of claim 8, wherein thefirst quality of service parameter for the failed logical circuit is anunspecified bit rate parameter.
 15. The apparatus of claim 8, whereinthe logical failover circuit comprises a dedicated failover logicalconnection in a failover data network.
 16. The apparatus of claim 15,wherein the dedicated failover logical connection comprises anetwork-to-network interface.
 17. The apparatus of claim 8, wherein thelogical failover circuit is identified by one of a data link connectionidentifier (DLCI) or a virtual path/virtual circuit identifier(VPI/VCI).
 18. A computer readable storage device comprisinginstructions which, when executed, cause a machine to perform a methodcomprising: when a first quality of service parameter for a failedlogical circuit is equal to or less than a second quality of serviceparameter for a logical failover circuit, rerouting data from the failedlogical circuit to the logical failover circuit without requiringauthorization from a customer to communicate the data at the secondquality of service parameter; and when the second quality of serviceparameter for the logical failover circuit is a lower level of qualitythan the first quality of service parameter for the failed logicalcircuit: prompting the customer for an authorization to communicate thedata via the logical failover circuit at the second quality of serviceparameter; when the authorization is received, rerouting the data fromthe failed logical circuit to the logical failover circuit; and when theauthorization is denied, not rerouting the data to the logical failovercircuit.
 19. The computer readable storage device of claim 18, whereinthe first quality of service parameter for the failed logical circuit isa constant bit rate parameter.
 20. The computer readable storage deviceof claim 18, wherein the first quality of service parameter for thefailed logical circuit is a constant bit rate parameter.